Systems and Methods for User Equipment Cooperation

ABSTRACT

Aspects of the present application provide methods and devices for use in User Equipment (UE) cooperation. A packet transmitted between a base station and a UE or between UEs includes a packet destination identifier that identifies a destination of the packet. A receiving the packet from a base station or another UE can determine whether the UE is the destination of the packet. When the UE is the destination of the packet, the UE decodes the packet. When the UE is not the destination of the packet, the UE forwards the packet to another UE. The packet may include a packet source identifier that can be used by the destination to determine where the packet originated. In some instances, the cooperative UEs do not need to decode the entire packet to be able to determine the destination of the packet and therefore can forward the packet along with less processing.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. Provisional patentapplication Ser. No. 16/743,597, filed on Jan. 15, 2020, which claimsthe benefit of priority of U.S. Provisional Patent Application No.62/794,261, filed on Jan. 18, 2019, which applications are herebyincorporated by reference in their entireties.

TECHNICAL FIELD

The present disclosure relates generally to wireless communications, andin particular embodiments, to User Equipment (UE) cooperation.

BACKGROUND

In some wireless communication systems, user equipments (UEs) wirelesslycommunicate with a base station to send data to the base station and/orreceive data from the base station. A wireless communication from a UEto a base station is referred to as an uplink (UL) communication. Awireless communication from a base station to a UE is referred to as adownlink (DL) communication. A wireless communication from a first UE toa second UE is referred to as a sidelink (SL) communication ordevice-to-device (D2D) communication.

Resources are required to perform uplink, downlink and sidelinkcommunications. For example, a base station may wirelessly transmitdata, such as a transport block (TB), to a UE in a downlink transmissionat a particular frequency and over a particular duration of time. Thefrequency and time duration used are examples of resources.

UE cooperation has been proposed to enhance reliability, throughput andcapacity. For example, UE cooperation can be used to provide diversityin space, time and frequency, and increase the robustness against fadingand interference. In UE cooperation, SL communications are used toestablish joint UE reception, where some of the UEs, referred to ascooperating UEs (CUEs), act as relays for other UEs, referred to astarget UEs (TUEs) to improve system throughput and coverage. However,joint UE reception using SL communications can also increase thecomplexity of the network communications, such as for hybrid-automaticrepeat request (HARQ) signaling. The HARQ mechanism is a link adaptationtechnique that can improve communications for erroneous data packets inwireless communication networks.

SUMMARY

Aspects of the present disclosure provide, for use with a group of UEs,using a packet destination identifier and optionally a packet sourceidentifier in UE cooperation. The benefit of using the packetdestination identifier is to avoid the ambiguity of the destination ofthe packet and thus the cooperating UE (CUE) and the target UE (TUE) inthe UE group know how to better handle the packet, by either forwardingit or decoding it. In some embodiments, it also avoids a privacy concernthat the other UEs may decode the data before forwarding it. In someembodiments, methodologies described herein could save the UE power inunnecessary decoding of data that is not intended for the UE.

According to an aspect of the disclosure, there is provided a methodinvolving receiving, by a first UE of a group of UEs, a packetcomprising a packet destination identifier that identifies a destinationof the packet and forwarding, by the first UE, the packet to a second UEor a base station based on the packet destination identifier withoutdecoding the entire packet.

In some embodiments, the packet destination identifier is included in aself-contained bit field or code block of the packet, the self-containedbit field or code block for identifying one or more UEs in the group ofUEs or a base station as a destination of the packet.

In some embodiments, the self-contained bit field or code block ismultiplexed with the data portion by puncturing or rate matching thedata portion.

In some embodiments, the packet destination identifier is included in aself-contained sequence, of a set of self-contained sequences, in a dataportion of the packet, the self-contained sequence for identifying oneor more UEs in the group of UEs or a base station as a destination ofthe packet.

In some embodiments, the self-contained sequence is multiplexed with thedata portion by puncturing or rate matching the data portion.

In some embodiments, the packet destination identifier is included in ascrambled demodulation reference signal (DMRS) for identifying one ormore UEs in the group of UEs or a base station as a destination of thepacket.

In some embodiments, the packet further includes a packet sourceidentifier that identifies a source of the packet, and the packet sourceidentifier is included in a self-contained bit field or code block ofthe packet, the self-contained bit field or code block for identifyingthe base station or one UE in the group of UEs as a source of thepacket.

In some embodiments, the packet further includes a packet sourceidentifier that identifies a source of the packet, and the packet sourceidentifier is included in a self-contained sequence, of a set ofself-contained sequences, in a data portion of the packet, theself-contained sequence for identifying the base station or one UE inthe group of UEs as a source of the packet.

In some embodiments, the self-contained sequence is multiplexed with thedata portion by puncturing or rate matching the data portion.

In some embodiments, the packet source identifier is included in ascrambled demodulation reference signal (DMRS) for identifying the basestation or one UE in the group of UEs as a source of the packet.

In some embodiments, the packet further comprises a UE group identifieror a target UE identifier (TUE ID).

According to an aspect of the disclosure, there is provided a userequipment (UE) including a processor and a computer-readable mediumhaving stored thereon computer-executable instructions. Thecomputer-executable instructions, when executed by the processor, causethe UE to receive a packet comprising a packet destination identifierthat identifies a destination of the packet and forward the packet to asecond UE or a base station based on the packet destination identifierwithout decoding the entire packet.

In some embodiments, the packet destination identifier is included in aself-contained bit field or code block of the packet, the self-containedbit field or code block for identifying one or more UEs in a group ofUEs or a base station as a destination of the packet.

In some embodiments, the self-contained bit field or code block ismultiplexed with the data portion by puncturing or rate matching thedata portion.

In some embodiments, the packet destination identifier is included in aself-contained sequence, of a set of self-contained sequences, in a dataportion of the packet, the self-contained sequence for identifying oneor more UEs in a group of UEs or a base station as a destination of thepacket.

In some embodiments, the self-contained sequence is multiplexed with thedata portion by puncturing or rate matching the data portion.

In some embodiments, the packet destination identifier is included in ascrambled demodulation reference signal (DMRS) for identifying one ormore UEs in a group of UEs or a base station as a destination of thepacket.

In some embodiments, the packet further includes a packet sourceidentifier that identifies a source of the packet, and the packet sourceidentifier is included in a self-contained bit field or code block ofthe packet, the self-contained bit field or code block for identifyingthe base station or one UE in a group of UEs as a source of the packet.

In some embodiments, the packet further includes a packet sourceidentifier that identifies a source of the packet, and the packet sourceidentifier is included in a self-contained sequence, of a set ofself-contained sequences, in a data portion of the packet, theself-contained sequence for identifying the base station or one UE in agroup of UEs as a source of the packet.

In some embodiments, the self-contained sequence is multiplexed with thedata portion by puncturing or rate matching the data portion.

In some embodiments, the packet source identifier is included in ascrambled demodulation reference signal (DMRS) for identifying the basestation or one UE in a group of UEs as a source of the packet.

In some embodiments, the packet further comprises a UE group identifieror a target UE identifier (TUE ID).

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present embodiments, and theadvantages thereof, reference is now made, by way of example, to thefollowing descriptions taken in conjunction with the accompanyingdrawings, in which:

FIG. 1 is a schematic diagram of a communication system in whichembodiments of the disclosure may occur.

FIGS. 2A and 2B are block diagrams of an example user equipment and basestation, respectively.

FIG. 3 is a block diagram illustrating an example of a network servingtwo UEs according to an aspect of the present disclosure.

FIG. 4 is a schematic diagram of a communications between a base stationand multiple user equipment in a UE group according to an embodiment ofthe present disclosure.

FIGS. 5A, 5B, 5C and 5D are examples of how a packet destinationidentifier or a packet source identifier can be transmitted in atime-frequency resource, according to embodiments of the presentdisclosure.

FIG. 6 is a schematic diagram showing an example of how UE cooperationoccurs between a base station and multiple user equipment in a UE groupaccording to an embodiment of the present disclosure.

FIG. 7 is a flow chart illustrating an example method performed by a UEaccording to an embodiment of the present disclosure.

FIG. 8 is a flow chart illustrating an example method performed by abase station according to an embodiment of the present disclosure.

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

For illustrative purposes, specific example embodiments will now beexplained in greater detail below in conjunction with the figures.

The embodiments set forth herein represent information sufficient topractice the claimed subject matter and illustrate ways of practicingsuch subject matter. Upon reading the following description in light ofthe accompanying figures, those of skill in the art will understand theconcepts of the claimed subject matter and will recognize applicationsof these concepts not particularly addressed herein. It should beunderstood that these concepts and applications fall within the scope ofthe disclosure and the accompanying claims.

Moreover, it will be appreciated that any module, component, or devicedisclosed herein that executes instructions may include or otherwisehave access to a non-transitory computer/processor readable storagemedium or media for storage of information, such as computer/processorreadable instructions, data structures, program modules, and/or otherdata. A non-exhaustive list of examples of non-transitorycomputer/processor readable storage media includes magnetic cassettes,magnetic tape, magnetic disk storage or other magnetic storage devices,optical disks such as compact disc read-only memory (CD-ROM), digitalvideo discs or digital versatile discs (i.e. DVDs), Blu-ray Disc™, orother optical storage, volatile and non-volatile, removable andnon-removable media implemented in any method or technology,random-access memory (RAM), read-only memory (ROM), electricallyerasable programmable read-only memory (EEPROM), flash memory or othermemory technology. Any such non-transitory computer/processor storagemedia may be part of a device or accessible or connectable thereto.Computer/processor readable/executable instructions to implement anapplication or module described herein may be stored or otherwise heldby such non-transitory computer/processor readable storage media.

UE cooperation can enhance the system by potentially improving coverageand capacity. UE cooperation can also improve the latency andreliability of the system. The UE cooperation can be achieved by a groupof UEs helping each other with the Uu interface link transmission andsidelink (SL) transmission. The Uu interface link is the interface thatallows data transfer between the base station and a UE. Embodiments ofthe present disclosure aid in providing coordination and cooperationamong UE(s) in the group of UEs in terms of transmission and receptionby providing a manner for each transmitted/received message to beidentified based on a packet destination identifier and a packet sourceidentifier. A UE in the group can identify whether it is the destinationUE, or not, based on the packet destination identifier, in someembodiments without decoding the entire packet. If the UE is thedestination UE, the UE can then decode the entire packet. If the UE isnot the destination UE, the UE can forward the packet to the destinationUE or a UE in a path to the destination UE or simply other UEs in a UEgroup. In some embodiments, once the destination UE has received anddecoded the packet, the destination UE can send a hybrid automaticrepeat request acknowledgement (HARQ-ACK) back to the sourceacknowledging the packet has been received. The destination UE may sendthe HARQ-ACK to the source directly, or through one or more UEs in thegroup to the source. It should be emphasized that the packet destinationidentifier and the packet source identifier in this embodiment refermore to the identifiers that are inserted and transmitted along withphysical channels such as physical control channel or physical sharedchannel. That is different from some identifiers that are contained inthe data format from higher layers.

FIGS. 1, 2A, 2B and 3 following below provide context for the networkand device that may be in the network and that may implement aspects ofthe present disclosure.

FIG. 1 illustrates an example communication system 100 in whichembodiments of the present disclosure could be implemented. In general,the system 100 enables multiple wireless or wired elements tocommunicate data and other content. The purpose of the system 100 may beto provide content (voice, data, video, text) via broadcast, narrowcast,user device to user device, etc. The system 100 may operate efficientlyby sharing resources such as bandwidth.

In this example, the communication system 100 includes electronicdevices (ED) 110 a-110 c, radio access networks (RANs) 120 a-120 b, acore network 130, a public switched telephone network (PSTN) 140, theInternet 150, and other networks 160. While certain numbers of thesecomponents or elements are shown in FIG. 1, any reasonable number ofthese components or elements may be included in the system 100.

The EDs 110 a-110 c are configured to operate, communicate, or both, inthe system 100. For example, the EDs 110 a-110 c are configured totransmit, receive, or both via wireless communication channels. Each ED110 a-110 c represents any suitable end user device for wirelessoperation and may include such devices (or may be referred to) as a userequipment/device (UE), wireless transmit/receive unit (WTRU), mobilestation, mobile subscriber unit, cellular telephone, station (STA),machine type communication device (MTC), personal digital assistant(PDA), smartphone, laptop, computer, touchpad, wireless sensor, orconsumer electronics device.

FIG. 1 illustrates an example communication system 100 in whichembodiments of the present disclosure could be implemented. In general,the communication system 100 enables multiple wireless or wired elementsto communicate data and other content. The purpose of the communicationsystem 100 may be to provide content (voice, data, video, text) viabroadcast, multicast, unicast, user device to user device, etc. Thecommunication system 100 may operate by sharing resources such asbandwidth.

In this example, the communication system 100 includes electronicdevices (ED) 110 a-110 c, radio access networks (RANs) 120 a-120 b, acore network 130, a public switched telephone network (PSTN) 140, theinternet 150, and other networks 160. Although certain numbers of thesecomponents or elements are shown in FIG. 1, any reasonable number ofthese components or elements may be included in the communication system100.

The EDs 110 a-110 c are configured to operate, communicate, or both, inthe communication system 100. For example, the EDs 110 a-110 c areconfigured to transmit, receive, or both via wireless or wiredcommunication channels. Each ED 110 a-110 c represents any suitable enduser device for wireless operation and may include such devices (or maybe referred to) as a user equipment/device (UE), wirelesstransmit/receive unit (WTRU), mobile station, fixed or mobile subscriberunit, cellular telephone, station (STA), machine type communication(MTC) device, personal digital assistant (PDA), smartphone, laptop,computer, tablet, wireless sensor, or consumer electronics device.

In FIG. 1, the RANs 120 a-120 b include base stations 170 a-170 b,respectively. Each base station 170 a-170 b is configured to wirelesslyinterface with one or more of the EDs 110 a-110 c to enable access toany other base station 170 a-170 b, the core network 130, the PSTN 140,the internet 150, and/or the other networks 160. For example, the basestations 170 a-170 b may include (or be) one or more of severalwell-known devices, such as a base transceiver station (BTS), a Node-B(NodeB), an evolved NodeB (eNodeB), a Home eNodeB, a gNodeB, atransmission and receive point (TRP), a site controller, an access point(AP), or a wireless router. Any ED 110 a-110 c may be alternatively oradditionally configured to interface, access, or communicate with anyother base station 170 a-170 b, the internet 150, the core network 130,the PSTN 140, the other networks 160, or any combination of thepreceding. The communication system 100 may include RANs, such as RAN120 b, wherein the corresponding base station 170 b accesses the corenetwork 130 via the internet 150, as shown.

The EDs 110 a-110 c and base stations 170 a-170 b are examples ofcommunication equipment that can be configured to implement some or allof the functionality and/or embodiments described herein. In theembodiment shown in FIG. 1, the base station 170 a forms part of the RAN120 a, which may include other base stations, base station controller(s)(BSC), radio network controller(s) (RNC), relay nodes, elements, and/ordevices. Any base station 170 a, 170 b may be a single element, asshown, or multiple elements, distributed in the corresponding RAN, orotherwise. Also, the base station 170 b forms part of the RAN 120 b,which may include other base stations, elements, and/or devices. Eachbase station 170 a-170 b transmits and/or receives wireless signalswithin a particular geographic region or area, sometimes referred to asa “cell” or “coverage area”. A cell may be further divided into cellsectors, and a base station 170 a-170 b may, for example, employmultiple transceivers to provide service to multiple sectors. In someembodiments, there may be established pico or femto cells where theradio access technology supports such. In some embodiments, multipletransceivers could be used for each cell, for example usingmultiple-input multiple-output (MIMO) technology. The number of RAN 120a-120 b shown is exemplary only. Any number of RAN may be contemplatedwhen devising the communication system 100.

The base stations 170 a-170 b communicate with one or more of the EDs110 a-110 c over one or more air interfaces 190 using wirelesscommunication links e.g. radio frequency (RF), microwave, infrared (IR),etc. The air interfaces 190 may utilize any suitable radio accesstechnology. For example, the communication system 100 may implement oneor more orthogonal or non-orthogonal channel access methods, such ascode division multiple access (CDMA), time division multiple access(TDMA), frequency division multiple access (FDMA), orthogonal FDMA(OFDMA), or single-carrier FDMA (SC-FDMA) in the air interfaces 190.

A base station 170 a-170 b may implement Universal MobileTelecommunication System (UMTS) Terrestrial Radio Access (UTRA) toestablish an air interface 190 using wideband CDMA (WCDMA). In doing so,the base station 170 a-170 b may implement protocols such as High SpeedPacket Access (HSPA), Evolved HPSA (HSPA+) optionally including HighSpeed Downlink Packet Access (HSDPA), High Speed Packet Uplink Access(HSUPA) or both. Alternatively, a base station 170 a-170 b may establishan air interface 190 with Evolved UTMS Terrestrial Radio Access (E-UTRA)using LTE, LTE-A, and/or LTE-B. It is contemplated that thecommunication system 100 may use multiple channel access functionality,including such schemes as described above. Other radio technologies forimplementing air interfaces include IEEE 802.11, 802.15, 802.16,CDMA2000, CDMA2000 1×, CDMA2000 EV-DO, IS-2000, IS-95, IS-856, GSM,EDGE, and GERAN. Of course, other multiple access schemes and wirelessprotocols may be utilized.

The RANs 120 a-120 b are in communication with the core network 130 toprovide the EDs 110 a-110 c with various services such as voice, data,and other services. The RANs 120 a-120 b and/or the core network 130 maybe in direct or indirect communication with one or more other RANs (notshown), which may or may not be directly served by core network 130, andmay or may not employ the same radio access technology as RAN 120 a, RAN120 b or both. The core network 130 may also serve as a gateway accessbetween (i) the RANs 120 a-120 b or EDs 110 a-110 c or both, and (ii)other networks (such as the PSTN 140, the internet 150, and the othernetworks 160).

The EDs 110 a-110 c communicate with one another over one or more SL airinterfaces 180 using wireless communication links e.g. radio frequency(RF), microwave, infrared (IR), etc. The SL air interfaces 180 mayutilize any suitable radio access technology, and may be substantiallysimilar to the air interfaces 190 over which the EDs 110 a-110 ccommunication with one or more of the base stations 170 a-170 c, or theymay be substantially different. For example, the communication system100 may implement one or more channel access methods, such as codedivision multiple access (CDMA), time division multiple access (TDMA),frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), orsingle-carrier FDMA (SC-FDMA) in the SL air interfaces 180. In someembodiments, the SL air interfaces 180 may be, at least in part,implemented over unlicensed spectrum.

In this disclosure, the SL transmissions between cooperating UEs may be“grant-free” transmissions or as a mode for data transmissions that areperformed without communicating dynamic scheduling. Grant-freetransmissions are sometimes called “configured grant”, “grant-less”,“schedule free”, or “schedule-less” transmissions. Grant-free SLtransmissions can also be referred to as SL “transmission withoutgrant”, “transmission without dynamic grant”, “transmission withoutdynamic scheduling”, or “transmission using configured grant”, forexample.

A configured grant transmission typically requires the receiver to knowthe parameters and resources used by the transmitter for thetransmission. However, in the context of SL transmissions, the receivingUE is typically not aware of the transmitting UE's configurationparameters, such as which UE is transmitting, the ultimate target of thedata (e.g., another UE), the time-domain and frequency-domaincommunication resources used for the transmission, and other controlinformation. Various methods may be used to provide the configurationparameters and control information necessary for enabling configuredgrant transmissions in SL. The various methods will, however, each incura respective overhead penalty. Embodiments of the present disclosureinclude at least some of those configuration parameters and/or controlinformation in the SL configured grant transmission, which may provideperformance and/or overhead benefits.

In addition, some or all of the EDs 110 a-110 c may includefunctionality for communicating with different wireless networks overdifferent wireless links using different wireless technologies and/orprotocols. Instead of wireless communication (or in addition thereto),the EDs may communicate via wired communication channels to a serviceprovider or switch (not shown), and to the internet 150. PSTN 140 mayinclude circuit switched telephone networks for providing plain oldtelephone service (POTS). Internet 150 may include a network ofcomputers and subnets (intranets) or both, and incorporate protocols,such as internet protocol (IP), transmission control protocol (TCP) anduser datagram protocol (UDP). EDs 110 a-110 c may be multimode devicescapable of operation according to multiple radio access technologies,and incorporate multiple transceivers necessary to support multipleradio access technologies.

FIGS. 2A and 2B illustrate example devices that may implement themethods and teachings according to this disclosure. In particular, FIG.2A illustrates an example ED 110, and FIG. 2B illustrates an examplebase station 170. These components could be used in the system 100 or inany other suitable system.

As shown in FIG. 2A, the ED 110 includes at least one processing unit200. The processing unit 200 implements various processing operations ofthe ED 110. For example, the processing unit 200 could perform signalcoding, data processing, power control, input/output processing, or anyother functionality enabling the ED 110 to operate in the communicationsystem 100. The processing unit 200 may also be configured to implementsome or all of the functionality and/or embodiments described in moredetail herein. Each processing unit 200 includes any suitable processingor computing device configured to perform one or more operations. Eachprocessing unit 200 could, for example, include a microprocessor,microcontroller, digital signal processor, field programmable gatearray, or application specific integrated circuit.

The ED 110 also includes at least one transceiver 202. The transceiver202 is configured to modulate data or other content for transmission byat least one antenna or Network Interface Controller (NIC) 204. Thetransceiver 202 is also configured to demodulate data or other contentreceived by the at least one antenna 204. Each transceiver 202 includesany suitable structure for generating signals for wireless or wiredtransmission and/or processing signals received wirelessly or by wire.Each antenna 204 includes any suitable structure for transmitting and/orreceiving wireless or wired signals. One or multiple transceivers 202could be used in the ED 110. One or multiple antennas 204 could be usedin the ED 110. Although shown as a single functional unit, a transceiver202 could also be implemented using at least one transmitter and atleast one separate receiver.

The ED 110 further includes one or more input/output devices 206 orinterfaces (such as a wired interface to the internet 150). Theinput/output devices 206 permit interaction with a user or other devicesin the network. Each input/output device 206 includes any suitablestructure for providing information to or receiving information from auser, such as a speaker, microphone, keypad, keyboard, display, or touchscreen, including network interface communications.

In addition, the ED 110 includes at least one memory 208. The memory 208stores instructions and data used, generated, or collected by the ED110. For example, the memory 208 could store software instructions ormodules configured to implement some or all of the functionality and/orembodiments described above and that are executed by the processingunit(s) 200. Each memory 208 includes any suitable volatile and/ornon-volatile storage and retrieval device(s). Any suitable type ofmemory may be used, such as random access memory (RAM), read only memory(ROM), hard disk, optical disc, subscriber identity module (SIM) card,memory stick, secure digital (SD) memory card, and the like.

As shown in FIG. 2B, the base station 170 includes at least oneprocessing unit 250, at least one transmitter 252, at least one receiver254, one or more antennas 256, at least one memory 258, and one or moreinput/output devices or interfaces 266. A transceiver, not shown, may beused instead of the transmitter 252 and receiver 254. A scheduler 253may be coupled to the processing unit 250. The scheduler 253 may beincluded within or operated separately from the base station 170. Theprocessing unit 250 implements various processing operations of the basestation 170, such as signal coding, data processing, power control,input/output processing, or any other functionality. The processing unit250 can also be configured to implement some or all of the functionalityand/or embodiments described in more detail above. Each processing unit250 includes any suitable processing or computing device configured toperform one or more operations. Each processing unit 250 could, forexample, include a microprocessor, microcontroller, digital signalprocessor, field programmable gate array, or application specificintegrated circuit.

Each transmitter 252 includes any suitable structure for generatingsignals for wireless or wired transmission to one or more EDs or otherdevices. Each receiver 254 includes any suitable structure forprocessing signals received wirelessly or by wire from one or more EDsor other devices. Although shown as separate components, at least onetransmitter 252 and at least one receiver 254 could be combined into atransceiver. Each antenna 256 includes any suitable structure fortransmitting and/or receiving wireless or wired signals. Although acommon antenna 256 is shown here as being coupled to both thetransmitter 252 and the receiver 254, one or more antennas 256 could becoupled to the transmitter(s) 252, and one or more separate antennas 256could be coupled to the receiver(s) 254. Each memory 258 includes anysuitable volatile and/or non-volatile storage and retrieval device(s)such as those described above in connection to the ED 110. The memory258 stores instructions and data used, generated, or collected by thebase station 170. For example, the memory 258 could store softwareinstructions or modules configured to implement some or all of thefunctionality and/or embodiments described above and that are executedby the processing unit(s) 250.

Each input/output device 266 permits interaction with a user or otherdevices in the network. Each input/output device 266 includes anysuitable structure for providing information to or receiving/providinginformation from a user, including network interface communications.

Additional details regarding the UEs 110 and the base stations 170 areknown to those of skill in the art. As such, these details are omittedhere for clarity.

FIG. 3 is a block diagram illustrating an example of a network 352serving two UEs 354 a and 354 b, according to one embodiment. The twoUEs 354 a and 354 b may be, for example, the two UEs 110 a and 110 b inFIG. 1. However, more generally this need not be the case, which is whydifferent reference numerals are used in FIG. 3.

The network 352 includes a BS 356 and a managing module 358. Themanaging module 358 instructs the BS 356 to perform actions. Themanaging module 358 is illustrated as physically separate from the BS356 and coupled to the BS 356 via a communication link 360. For example,the managing module 358 may be part of a server in the network 352.Alternatively, the managing module 358 may be part of the BS 356.

The managing module 358 includes a processor 362, a memory 364, and acommunication module 366. The communication module 366 is implemented bythe processor 362 when the processor 362 accesses and executes a seriesof instructions stored in the memory 364, the instructions defining theactions of the communication module 366. When the instructions areexecuted, the communication module 366 causes the BS 356 to perform theactions described herein so that the network 352 can establish,coordinate, instruct, and/or control a UE group. Alternatively, thecommunication module 366 may be implemented using dedicated circuitry,such as an application specific integrated circuit (ASIC) or aprogrammed field programmable gate array (FPGA).

The UE 354 a includes a communication subsystem 370 a, two antennas 372a and 374 a, a processor 376 a, and a memory 378 a. The UE 354 a alsoincludes a communication module 380 a. The communication module 380 a isimplemented by the processor 376 a when the processor 376 a accesses andexecutes a series of instructions stored in the memory 378 a, theinstructions defining the actions of the communication module 380 a.When the instructions are executed, the communication module 380 acauses the UE 354 a to perform the actions described herein in relationto establishing and participating in a UE group. Alternatively, themodule 380 a may be implemented by dedicated circuitry, such as an ASICor an FPGA.

The communication subsystem 370 a includes processing andtransmit/receive circuitry for sending messages from and receivingmessages at the UE 354 a. Although one communication subsystem 370 a isillustrated, the communication subsystem 370 a may be multiplecommunication subsystems. Antenna 372 a transmits wireless communicationsignals to, and receives wireless communications signals from, the BS356. Antenna 374 a transmits SL communication signals to, and receivesSL communication signals from, other UEs, including UE 354 b. In someimplementations there may not be two separate antennas 372 a and 374 a.A single antenna may be used. Alternatively, there may be severalantennas, but not separated into antennas dedicated only to SLcommunication and antennas dedicated only to communicating with the BS356.

SL communications could be over Wi-Fi, in which case the antenna 374 amay be a Wi-Fi antenna. Alternatively, the SL communications could beover Bluetooth™, in which case the antenna 374 a may be a Bluetooth™antenna. SL communications could also or instead be over licensed orunlicensed spectrum.

The UE 354 b includes the same components described above with respectto the UE 354 a. That is, UE 354 b includes communication subsystem 370b, antennas 372 b and 374 b, processor 376 b, memory 378 b, andcommunication module 380 b.

The UE 354 a is designated as a target UE (TUE) and will therefore becalled TUE 354 a. The UE 354 b is a cooperating UE (CUE) and willtherefore be called CUE 354 b. The CUE 354 b may be able to assist withwireless communications between the BS 356 and TUE 354 a if a UE groupwere to be established that included TUE 354 a and CUE 354 b.

UE 354 a may be specifically chosen as the target UE by the network 352.Alternatively, the UE 354 a may itself determine that it wants to be atarget UE and inform the network 352 by sending a message to the BS 356.Example reasons why UE 354 a may choose or be selected by the network352 to be a target UE include: low wireless channel quality between theUE 354 a and the BS 356, many packets to be communicated between the BS356 and the UE 354 a, and/or the presence of a cooperating UE that is agood candidate for helping with communications between the BS 356 andthe UE 354 a.

UE 354 a need not always stay a target UE. For example, UE 354 a maylose its status as a target UE once there is no longer a need or desirefor assistance with wireless communications between UE 354 a and the BS356. UE 354 a may assist another target UE that is a cooperating UE at alater time. In general, a particular UE may sometimes be a target UE andother times may be a cooperating UE assisting another target UE. Also,sometimes a particular UE may be both a target UE receiving assistancefrom one or more cooperating UEs and also a cooperating UE itselfassisting another target UE. In the examples below, the UE 354 a actsonly as a target UE, i.e., TUE 354 a, and the UE 354 b is a cooperatingUE to the TUE 354 a, i.e., CUE 354 b.

FIG. 3 illustrates a system in which embodiments could be implemented.In some embodiments, a UE includes a processor, such as 376 a, 376 b inFIG. 3, and a non-transitory computer readable storage medium, such as378 a, 378 b in FIG. 3, storing programming for execution by theprocessor. A non-transitory computer readable storage medium could alsoor instead be provided separately, as a computer program product.

In such embodiments, programming could include instructions to: receive,by the UE, a packet comprising a UE group identifier and furthercomprising a packet destination identifier that identifies a destinationUE and determining, by the UE, if the UE is the destination UE. When theUE is the destination UE, the UE decoding the packet and when the UE isnot the destination UE, the UE forwarding the packet to another UE.

FIG. 4 illustrates three different types of packet transmissions thatmay occur between a base station and a group of UEs that are predefinedas being in a same group. FIG. 4 includes a base station (gNB) 410 andseveral UEs (420 a, 420 b, 420 c, 420 d, 420 e and 420 f) that are partof UE group 430. The base station 410 can transmit and receive from UEs,for example as indicated by Uu downlink (DL) transmission 412 to UE 420a and by Uu uplink (UL) transmission 414 from UE 420 f. The UEs cantransmit and receive amongst themselves as indicated by sidelink (SL)transmission 422 between UE 420 a and UE 420 b, by SL transmission 424between UE 420 c and UE 420 d and by SL transmission 426 between UE 420e and UE 420 f. While SL transmissions 422, 424 and 426 are shown in asingle direction, it is understood that the SL transmissions can bebidirectional.

Type #1: The transmission is between a base station and a UE in apredefined UE group

The base station sends a packet in Uu DL by multicasting to a group ofUEs. Transmission 412 in FIG. 4 is an example of this type oftransmission. The cyclic redundancy code (CRC) of the packet can bescrambled by a target UE (TUE) ID or a group UE ID that is used toidentify UEs in the predefined group of UEs. The TUE ID would typicallyby considered a type of global identifier of the UE that is the targetdestination of the packet. An example of this is a Radio NetworkTemporary Identifier (RNTI). The RNTI is a 16-bit long identifier thatis assigned by the base station regardless of whether the UE isperforming UE cooperation or not. The RNTI can be used to scramble theCRC and decoded information bits of the packet for the TUE. The UEs inthe group could receive the packet and identify a destination for thepacket, i.e. the destination UE. If the packet is not for the UE, theUE, acting as a cooperating UE (CUE), can forward the packet throughamplify and forward (A-F) or decode and forward (D-F) methods. In someembodiments, the packet is forwarded using grant free (GF) transmission,also known as configured grant transmission. If a UE receives andidentifies the packet is for itself, the UE can decode the packet. Thetarget UE (TUE) can identify a source of the packet and send aHybrid-Automatic Repeat Request (HARQ) acknowledgement (ACK) to thesource, either directly or via one or more CUE.

Type #2: The transmission is between UEs within the UE group

The UE(s) in the UE group can send a packet using SL to another UE. SLtransmissions 422, 424 and 426 in FIG. 4 are examples of this type oftransmission. In some embodiments this may including using a configuredgrant transmission. The CRC of the packet can be scrambled by a targetUE (TUE) ID or the group UE ID. The UEs in the UE group can receive thepacket and identify a destination for the packet. If the packet is notfor the UE, the UE can forward the packet through A-F or D-F methods. Insome embodiments, the packet is forwarded using configured granttransmission. If the UE receives and identifies the packet is foritself, the UE can decode the packet. The TUE can identify a source ofthe packet and send a HARQ ACK to the source, either directly or via oneor more CUE.

Type #3: The transmission is from a UE in a predefined UE group to abase station

If the UE knows, or can determine, that the UE is within the coveragearea of Uu UL, the UE can send the packet directly to the base stationusing Uu UL. Transmission 414 in FIG. 4 is an example of this type oftransmission. In some embodiments, the packet is transmitted usingconfigured grant transmission. If the UE in the UE group knows, or candetermine, that the UE is not within the coverage area of Uu UL, the UEsends the packet using SL to one or more UEs. In some embodiments, thepacket is transmitted using configured grant transmission. The CRC ofthe packet can be scrambled by the TUE ID, or the group UE ID. The UEsin the UE group can receive the packet and identify a destination forthe packet. If the packet is not for the UE, the UE in the UE group canforward the packet through A-F or D-F methods. In some embodiments, thepacket is forwarded using configured grant transmission. If the UEreceives and identifies the packet is for the base station, and the UEis within the coverage area of Uu UL, the UE can transmit the packetdirectly to the base station using Uu UL. In some embodiments, thepacket is transmitted using configured grant transmission.

The packets in these three types of transmissions could carry one ofdata or control information or a combination of data and controlinformation from lower or higher layers.

In some embodiments of the present disclosure, as part of a UEcooperation process, a packet destination identifier, or packetdestination ID for simplicity, is proposed to facilitate forwarding ofpackets for the three types of transmissions described above. The packetdestination ID is used to indicate a final destination of the packet,i.e. the destination UE. The packet destination ID can be transmitted inany one of a number of different ways. The packet destination identifieris a relative identifier for the UE. It is intended for use when a UE ispart of a group for UEs, in particular for UE cooperation. The packetdestination identifier may be seen as a specific identifier with respectto the group of UEs. For example, if a group of UEs includes ten UEs, UE#1 could be assigned index #1, UE #2 could be assigned index #2, and soon. As a number of UEs in the group is typically a low number, theindices of the UEs can be captured by a bit length of, for example (butnot intended to be limiting), 3 to 8 bits. In a particular example, 3binary bits could be used to indicate a UE index for each UE in a groupof eight UEs. The packet destination identifier is different from the UERNTI, which is a global UE identifier. The packet destination identifiercould be provided to other UEs in the group, without having to disclosethe UE RNTI to other UEs. This has the benefit of lower overhead becauseof the small bit length of the packet destination identifier, as well asincreased privacy because other UEs in the group are not provided withan explicit identifier of the UE, only a relative identifier of thepacket destination. In some embodiments, the packet destination ID isembedded in the data portion or the control information portion of aphysical channel such as a physical control channel or a physical shareddata channel, or both, in the format of a self-contained bit field orcode block. A bit combination could indicate one or multiple UE(s) in aUE group. For example, the bit combination may identify each UE using anindex value associated with the UE that has been assigned within the UEgroup. If there were eight UEs in the UE group, a three bit combinationcould be used to identify each of the UEs. Alternatively, in someembodiments, a bit map could be used to indicate the UE index in a UEgroup. For example, if there are eight UE in the UE group, an eight-bitbit map, where each bit in the bit map represents a respective UE in thegroup, could be used to identify one or multiple UE in the group as theTUE.

In some embodiments, the packet destination ID is embedded in the dataportion in a format of one of a set of self-contained sequences. In someembodiments, a single sequence in each set of sequences is used toidentify one or multiple of the UEs in the UE group.

In some embodiments, the packet destination ID can be used to scrambledemodulation reference signals (DMRS) sequences. In such a scenario, thepacket destination identifier may be used to initiate a scramblingfunction to generate a DMRS sequence.

In some embodiments, the packet may also include a packet sourceidentifier (ID) to indicate an original source of the packet, i.e. abase station or CUE. In some embodiments, the packet source ID is arelative and possibly temporary identifier in much the same way as thepacket destination ID. When setting up the group of cooperating UEs, thebase station may designate itself an index value to be included in thegroup. This index value could then be used as the packet source ID whenthe base station is the source of the packet. When a UE of the group ofcooperating UEs is a source of the packet, the index designated by thebase station for the UE can be used as the packet source ID. The packetsource ID can be transmitted using similar alternatives as the packetdestination ID, i.e. a bit field or code block, a sequence, or a DMRSsequence.

In some embodiments, the packet destination ID and the packet source IDuse different resources. For example, different bit fields, differentcode block, different sequences, different scrambling sequences for theDMRS. Alternatively, the packet destination ID and the packet source IDcould be coded jointly.

FIGS. 5A, 5B, 5C and 5D illustrate several different examples on how thepacket destination ID and the packet source ID could be transmitted.

Each of FIGS. 5A, 5B, 5C and 5D illustrate a representation of a twodimensional time-frequency resource. Time is along the x-axis andfrequency is along the y-axis. The time-frequency resource may be usedfor transmitting both data and control information.

FIGS. 5A and 5B show that the packet destination ID, or the packetsource ID, could be located in the data portion of the allocatedresource. In some embodiments, the packet destination ID, or the packetsource ID, may be within the physical downlink shared channel (PDSCH).The bit field or code block could either be localized in single location505 of the allocated resource 500, as shown in FIG. 5A, or distributedwithin multiple portions 515 of the allocated resource 510, as shown inFIG. 5B. The bits that indicate the packet destination ID or the packetsource ID could be either coded or not coded (as bit-field). If coded,the packet destination ID or the packet source ID could be located in acode block all together, as shown in FIG. 5A, or distributed in the datapart, as shown in FIG. 5B in which the packet destination ID and/or thepacket source ID are coded separately from the data or controlinformation. In a scenario when the code block is localized, the codeblock could be located at the beginning of the data portion, such as ina first physical resource block (PRB) and a first symbol. In a scenariowhen the code block is distributed, the code block bits could be spreadover a first symbol or across multiple symbols in a slot. In someembodiments, puncturing or rate matching could be applied to the dataportion when the packet destination ID, or the packet source ID, ismultiplexed into the data portion.

FIG. 5C shows an example in which one of a set of sequences can be usedto indicate either of a packet destination ID or packet source ID. Thesequence 525 is located in a allocated resource 520. While the sequence525 is shown to encompass a symbol over the entire bandwidth of theallocated resource, this is only an example and it is to be understoodthat the sequence may encompass less than the entire bandwidth and mayoccur over multiple symbols. The slot may be, for example, a symbol. Anexample of a type of sequence is a Zadoff-Chu (ZC) sequence, but othertypes of sequences are contemplated. Different sequences within the setof sequences could be used to indicate respective packet destination IDsor source packet IDs. The sequence may be transmitted before the dataportion starts or inserted into the data portion. The sequence may spana whole symbol or a portion of one or more symbols. In some embodiments,puncturing or rate matching could be applied to the data portion whenthe sequence is multiplexed into the data portion.

FIG. 5D shows an example of how DMRS 535 could be used to indicateeither the packet destination ID or the source destination ID in theallocated resource 530. Generating the scrambled DMRS could be initiatedby the packet destination ID, or the packet source ID, and thus thepacket destination ID, or the source destination, can be derived fromthe received DMRS.

In some embodiments, the packet destination ID or the packet source IDcould be derived by one or more parameters. A first example parameter isthe target UE ID (for the packet destination ID) or the source UE ID(for the packet source ID). The target UE ID or the source UE ID mayinclude a radio network temporary identifier (RNTI) or other higherlayer configured identifier. A second example parameter is a target UEindex or a source UE index of the UE group. A third example parameter isa group ID containing the target UE or the source UE. A fourth exampleparameter is a different ID that is assigned to the target UE or thesource UE by the base station. A fifth example parameter is a HARQprocess identifier (ID) of the transmission. A sixth example parameteris a cell ID or other identifier of the base station (or transmitreceive point (TRP) that is associated with the UE group on the Uu link.

With the use of packet destination ID or packet source ID, the procedureof packet transmission in a UE group can be implemented as describedbelow, with reference to FIG. 6. FIG. 6 has a similar arrangement ofnetwork elements as FIG. 4, a base station 610 and six UEs 620 a, 620 b,620 c, 620 d, 620 e and 620 f in a predefined UE group 630.

A preliminary process that occurs, but is not discussed in detail, isthe organization of the group of UEs. Once the group has been defined orformed, the base station (gNB) 610 transmits a multicast message to theUEs of the group. This is shown in the form of multicast transmissions612, 614, 616 and 618 from the base station 610 to UE 620 b, UE 620 c,UE 620 a and UE 620 f, respectively. Despite the multicast transmissionshaving different reference characters, this is for the purpose ofdescribing the figure and it is to be understood that the multicasttransmission is the same to all the UEs in the group. Multicasttransmissions 612, 614, and 616 are not successfully received at UE 620b, UE 620 c, UE 620 a, respectively. However, multicast transmission 618is successfully received at UE 620 f. The unsuccessful reception of apacket here means the UE does not detect the control channel thatschedules the packet of the data portion. After a packet is received byUE 620 f, the UE 620 f can identify whether the packet is for UE 620 for not, without decoding the entirety of packet. For example, the UEdecodes at least the portion of the packet that includes the packetdestination identifier. If the packet is for UE 620 f, the UE can try todecode the packet. If not, the UE could forward the packet. In theexample of FIG. 6, UE 620 f determines that the packet is not for UE 620f and forwards the packet to other UEs, in this case UE 620 c and UE 620d in transmissions 622 and 624, respectively. Such procedure will berepeated until the packet destination UE receives the packet and decodesit. Packet forwarding transmissions 622 is not successfully received atUE 620 c. However, packet forwarding transmission 624 is successfullyreceived at UE 620 d. After the packet is received by UE 620 d, the UE620 d can identify whether the packet is for UE 620 d or not, withoutdecoding the entirety of packet. UE 620 d determines that the packet isnot for UE 620 d and forwards the packet to UE 620 c in packetforwarding transmission 626. After the packet is received by UE 620 c,the UE 620 c identifies that the packet is for UE 620 c. In someembodiments, the packet destination UE, in FIG. 6 this is 620 c,determines the source of the packet by checking the packet source ID.The packet destination UE can feedback a HARQ-ACK to another UE in thegroup or to the base station, according to the packet source ID.

The UE cooperation strategies include strategies for handling degradedchannel signals. For instance, one or more CUEs perform a decode andforward (D-F) strategy to support communications for one or more TUEs inthe group of UEs. The one or more CUEs can also perform an amplify andforward (A-F) strategy to support the communications of the one or moreTUEs. The strategies for degraded channel signals also includehierarchical modulation and/or coding. For example, a CUE receives anddecodes a first modulated signal on a downlink and then forwards thefirst signal to a TUE, which also directly receives and decodes a secondmodulated signal (via a direct link from a BS). The TUE then combinesthe first and second signals to process the downlink data. This isreferred to as soft combining. Similarly, two modulated signals (ormore) on the uplink can be separately received by the network from a CUEand a TUE and then combined for processing.

The UE cooperation strategies also include strategies for handlingnon-degraded channel signals. Such strategies include joint reception onthe downlink between one or more CUEs and one or more TUEs in the groupof UEs, for example using log-likelihood ratio (LLR) combining ormultiple-input and multiple-output (MIMO) schemes. The strategies fornon-degraded channel signals also include joint transmission on theuplink between one or more TUEs and one or more CUEs, such as usingEavesdrop or HARQ schemes. The CUEs with the TUEs may switch between anyof the UE cooperation strategies above based on the network channelconditions, e.g., according to whether degraded or non-degraded channelsignals are detected. In an embodiment, a CUE estimates a channelbetween the CUE and the network and forwards the estimated channel to acorresponding TUE. The TUE also estimates a channel between the TUE andthe network, and then combines the channels to obtain a combined channelfor joint reception/transmission.

FIG. 7 is an example flow diagram 700 that describes a method of how UEcooperation can be performed in accordance with an aspect of thisdisclosure. At 710, a UE in a predefined group of UEs receives a packetcomprising a packet destination identifier that identifies a destinationof a packet. At 720, the UE determines whether the UE is the destinationof the packet. If the UE is not the destination of the packet, at 740the UE forwards the packet to another UE. After 740, the UE thatreceives the packet is a new UE so the process returns to 710.

If the UE is the destination of the packet, at 730 the UE decodes thepacket. After the UE has decoded the packet in 730, the UE optionallydetermines the source of the packet at 750 by checking a packet sourceidentifier that is part of the packet. At 760, the UE optionallytransmits the HARQ-ACK to a base station that is the source or anotherUE that will forward the HARQ-ACK to the base station that is the sourceor a further UE in a path in the direction of the source.

FIG. 8 is an example flow diagram 800 that describes a method of how UEcooperation can be performed in accordance with an aspect of thisdisclosure. At 810, a source device transmits a packet comprising apacket destination identifier that identifies a destination. The sourcedevice could be a base station transmitting to a UE or group of UEs or aUE transmitting to one or more UEs or a base station. At 820, the sourcedevice receives a Hybrid-Automatic Repeat Request (HARQ) acknowledgement(ACK) from a UE of the group of UEs or a base station.

One possible application of sidelink (SL) communications is vehicle toeverything/anything (V2X) communication, for example, which is anincreasingly important new category of communication that may becomewidespread in next generation wireless communication networks, such as5G New Radio (NR) systems. V2X refers to a category of communicationscenarios, including communication from a vehicle to another vehicle(V2V), vehicle to infrastructure (V2I), and vehicle to pedestrian (V2P),for example. In general, a vehicle communicating in a network isconsidered user equipment (UE).

The communication in V2X systems may be performed using links betweenthe network and the UE, such as an uplink (UL) and a downlink (DL). TheUL is a wireless communication from a UE to a base station (BS), and theDL is a wireless communication from a BS to a UE. In V2V communicationusing the UL and DL, data is transmitted from a transmitting UE to a BS,and then transmitted from the BS to a receiving UE.

Alternatively, some of the V2X communication scenarios may be device todevice (D2D) communications, in which case the transmission in V2Xsystems may be performed between the transmitting UE and receiving UEusing a sidelink (SL). The SL allows data to be transmitted directlyfrom the transmitting UE to the receiving UE, without forwarding thedata via the BS.

In general, the SL and UE cooperation may enhance the reliability,throughput, and capacity of any wireless communications. However,successful UE cooperation requires proper management of the SL betweenCUEs and TUEs in order to reduce interference and improve UE cooperationbenefits.

It should be appreciated that one or more steps of the embodimentmethods provided herein may be performed by corresponding units ormodules. For example, a signal may be transmitted by a transmitting unitor a transmitting module. A signal may be received by a receiving unitor a receiving module. A signal may be processed by a processing unit ora processing module. The respective units/modules may be hardware,software, or a combination thereof. For instance, one or more of theunits/modules may be an integrated circuit, such as field programmablegate arrays (FPGAs) or application-specific integrated circuits (ASICs).It will be appreciated that where the modules are software, they may beretrieved by a processor, in whole or part as needed, individually ortogether for processing, in single or multiple instances as required,and that the modules themselves may include instructions for furtherdeployment and instantiation.

Although a combination of features is shown in the illustratedembodiments, not all of them need to be combined to realize the benefitsof various embodiments of this disclosure. In other words, a system ormethod designed according to an embodiment of this disclosure will notnecessarily include all of the features shown in any one of the Figuresor all of the portions schematically shown in the Figures. Moreover,selected features of one example embodiment may be combined withselected features of other example embodiments.

According to a first example of the present disclosure, there isprovided a method for User Equipment (UE) cooperation. The methodinvolves a UE in a predefined group of UEs receiving a packet comprisinga packet destination identifier that identifies a destination of thepacket and the UE determining whether the UE is the destination of thepacket. When the UE is the destination of the packet, the UE decodes thepacket. When the UE is not the destination of the packet, the UEforwards the packet to another UE or a base station.

According to a further embodiment of the first example, the methodincludes the UE determining if the UE is the destination of the packetis performed without having to decode the entire packet.

According to a further embodiment of the first example, the packetfurther includes a UE group identifier or a target UE identifier (TUEID).

According to a further embodiment of the first example, the TUE ID is aRadio Network Temporary Identifier (RNTI) of the target UE.

According to a further embodiment of the first example, the packetfurther includes a packet source identifier that identifies a source ofthe packet, and when the UE is the destination of the packet, the UEdetermining the source of the packet by checking the packet sourceidentifier.

According to a further embodiment of the first example, the methodfurther involves, after successfully decoding the packet, the UEtransmitting a Hybrid-Automatic Repeat Request (HARQ) acknowledgement(ACK) to the source of the packet.

According to a further embodiment of the first example, the methodfurther involves, the UE transmitting the HARQ-ACK to: a base stationthat is the source of the packet; or another UE that will forward theHARQ-ACK to the base station that is the source of the packet or afurther UE in a path in the direction of the source of the packet.

According to a further embodiment of the first example, the methodfurther involves, the UE receiving a Hybrid-Automatic Repeat Request(HARQ) acknowledgement (ACK) from the another UE.

According to a further embodiment of the first example, forwarding thepacket to the another UE includes: amplifying the packet and forwardingthe packet to the another UE; or decoding the packet, re-encoding thepacket and forwarding the packet to the another UE.

According to a further embodiment of the first example, the packetcomprises data or control information, or both.

According to a further embodiment of the first example, the packetdestination identifier is included in a self-contained bit field or codeblock.

According to a further embodiment of the first example, theself-contained bit field or code block identifies one or more UEs in thegroup of UEs as destinations of the packet.

According to a further embodiment of the first example, theself-contained bit field or code block is either: localized in a singleportion of a data transmission; or distributed in multiple portionsacross a data transmission.

According to a further embodiment of the first example, the packetdestination identifier is included in self-contained sequence of a setof self-contained sequences in a data portion.

According to a further embodiment of the first example, theself-contained sequence: spans less than one symbol; spans one symbol;or spans more than one symbol.

According to a further embodiment of the first example, theself-contained sequence multiplexes with or punctures in the dataportion.

According to a further embodiment of the first example, the packetdestination identifier is included in a scrambled demodulation referencesignal (DMRS).

According to a further embodiment of the first example, the packetsource identifier is included in a self-contained bit field or codeblock.

According to a further embodiment of the first example, theself-contained bit field or code block identifies one or more UEs in thegroup of UEs as destinations of the packet.

According to a further embodiment of the first example, theself-contained bit field or code block is either: localized in a singleportion of a data transmission; or distributed in multiple portionsacross a data transmission.

According to a further embodiment of the first example, the packetsource identifier is included in self-contained sequence of a set ofself-contained sequences in a data portion.

According to a further embodiment of the first example, theself-contained sequence: spans less than one symbol; spans one symbol;or spans across more than one symbol.

According to a further embodiment of the first example, theself-contained sequence multiplexes with or punctures in the dataportion.

According to a further embodiment of the first example, the packetsource identifier is included in a scrambled demodulation referencesignal (DMRS).

According to a further embodiment of the first example, the packetdestination identifier and the source identifier are transmitted ondifferent transmission resources.

According to a further embodiment of the first example, the packetdestination identifier and the source identifier are received ondifferent transmission resources.

According to a further embodiment of the first example, the packet istransmitted or received on a resource by a configured granttransmission.

According to a further embodiment of the first example, the packetdestination identifier or the packet source identifier, or both, isderived by one or more of the following parameters: a radio networktemporary identifier (RNTI) or higher layer configured identifier (ID);a target UE index or a source UE index, or both, in the UE group; agroup ID comprises a target UE, or a source UE, or both; anotheridentifier type that is assigned by the base station to the target ID orsource ID, or both; a Hybrid-Automatic Repeat Request (HARQ) process IDof a transmission including the packet; and a cell ID or an indicationof the base station that is associated with UE group on a base stationto UE link.

According to a second example of the present disclosure, there isprovided a method for User Equipment (UE) cooperation. The methodinvolves a source device transmitting a packet comprising a packetdestination identifier that identifies a destination UE in a group ofUEs or a base station and the source device receiving a Hybrid-AutomaticRepeat Request (HARQ) acknowledgement (ACK) from a UE of the group ofUEs or the base station.

According to a further embodiment of the second example, the sourcedevice is: a base station; or a UE.

According to a further embodiment of the second example, the UE iseither: a destination UE; or a UE that has received the HARQ-ACK fromthe destination UE or a UE in a path from the destination UE.

According to a further embodiment of the second example, the methodfurther involves, a UE group identifier or a target UE identifier (TUEID).

According to a further embodiment of the second example, the TUE ID is aRadio Network Temporary Identifier (RNTI) of the target UE.

According to a further embodiment of the second example, the packetfurther includes a packet source identifier that identifies the sourcedevice as a source of the packet.

According to a further embodiment of the second example, the packetincludes data or control information, or both.

According to a further embodiment of the second example, the packetdestination identifier is included in a self-contained bit field or codeblock.

According to a further embodiment of the second example, theself-contained bit field or code block indicates one or more UEs in thegroup of UEs as destinations of the packet.

According to a further embodiment of the second example, theself-contained bit field or code block is either: localized in a singleportion of a data transmission; or distributed in multiple portionsacross a data transmission.

According to a further embodiment of the second example, the packetdestination identifier is included in a self-contained sequence of a setof self-contained sequences in a data portion.

According to a further embodiment of the second example, theself-contained sequence: spans less than a one symbol; spans one symbol;or spans across more than one symbol.

According to a further embodiment of the second example, theself-contained sequence multiplexes with or punctures in the dataportion.

According to a further embodiment of the second example, the packetdestination identifier is included in a scrambled demodulation referencesignal (DMRS).

According to a further embodiment of the second example, the packetsource identifier is included in a self-contained bit field or codeblock.

According to a further embodiment of the second example, theself-contained bit field or code block indicates one or more UEs in thegroup of UEs as destinations of the packet.

According to a further embodiment of the second example, theself-contained bit field or code block is either: localized in a singleportion of a data transmission; or distributed in multiple portionsacross a data transmission.

According to a further embodiment of the second example, the packetsource identifier is included in a self-contained sequence of a set ofself-contained sequences in a data portion.

According to a further embodiment of the second example, theself-contained sequence: spans less than a one symbol; spans one symbol;or spans more than one symbol.

According to a further embodiment of the second example, theself-contained sequence multiplexes with or punctures in the dataportion.

According to a further embodiment of the second example, the packetsource identifier is included in a scrambled demodulation referencesignal (DMRS).

According to a further embodiment of the second example, the packetdestination identifier and the source identifier are transmitted ondifferent transmission resources.

According to a further embodiment of the second example, the HARQ-ACK isreceived on a resource by configured grant transmission.

According to a further embodiment of the second example, when the sourcedevice is a UE, the UE transmitting to: another UE in the group of UEs;or a base station.

According to a third example of the present disclosure, there isprovided a User Equipment (UE) for use in UE cooperation with a group ofUEs. The UE includes a processor; and a computer-readable medium havingstored thereon computer-executable instructions. When executed by theprocessor, the computer-executable instructions cause the UE to: receivea packet comprising a packet destination identifier that identifies adestination of the packet and determine whether the UE is thedestination of the packet. When the UE is the destination of the packet,the UE decodes the packet. When the UE is not the destination of thepacket, the UE forwards the packet to another UE or a base station.

According to a further embodiment of the third example, the packetfurther includes a packet source identifier that identifies a source ofthe packet, and when the UE is the destination of the packet, thecomputer-executable instructions are configured to determine the sourceof the packet by checking the packet source identifier.

According to a further embodiment of the third example, aftersuccessfully decoding the packet, the computer-executable instructionsare configured to transmit a Hybrid-Automatic Repeat Request (HARQ)acknowledgement (ACK) to the source of the packet.

According to a further embodiment of the third example, the UE isconfigured to transmit the HARQ-ACK to: a base station that is thesource of the packet; or another UE that will forward the HARQ-ACK tothe base station that is the source of the packet or a further UE in apath in the direction of the source of the packet.

According to a further embodiment of the third example, the UE isconfigured to receive a Hybrid-Automatic Repeat Request (HARQ)acknowledgement (ACK) from the another UE.

According to a fourth example of the present disclosure, there isprovided a source device for use in UE cooperation with a group of UEs.The source device includes a processor; and a computer-readable mediumhaving stored thereon computer-executable instructions. When executed bythe processor, the computer-executable instructions cause the sourcedevice to: transmit a packet comprising a packet destination identifierthat identifies a destination UE in a group of UEs or a base station;and receive a Hybrid-Automatic Repeat Request (HARQ) acknowledgement(ACK) from a UE of the group of UEs or the base station.

According to a further embodiment of the fourth example, the sourcedevice is: a base station; or a UE.

According to a further embodiment of the fourth example, when the sourcedevice is a UE, the UE transmitting to: another UE in the group of UEs;or a base station.

While this disclosure has been described with reference to illustrativeembodiments, this description is not intended to be construed in alimiting sense. Various modifications and combinations of theillustrative embodiments, as well as other embodiments of thedisclosure, will be apparent to persons skilled in the art uponreference to the description. It is therefore intended that the appendedclaims encompass any such modifications or embodiments.

What is claimed is:
 1. A method comprising: receiving, by a first userequipment (UE), a packet comprising a packet destination identifier (ID)that identifies a destination of the packet, wherein the packetdestination identifier is a higher layer ID that is configurable; andforwarding, by the first UE, the packet to a second UE or a base stationbased on the packet destination identifier.
 2. The method of claim 1,wherein the packet destination identifier is different from a radionetwork temporary identifier (RNTI).
 3. The method of claim 1, whereinthe packet destination identifier uniquely identifies the second UE as afinal destination of the packet or uniquely identifies the base stationas the destination of the packet.
 4. The method of claim 1, wherein thepacket destination identifier is the higher layer ID included in aself-contained bit field.
 5. The method of claim 1, wherein the packetdestination identifier is the higher layer ID multiplexed into a dataportion of the packet.
 6. The method of claim 1, the receivingcomprising: receiving, by the first UE, the packet from a source deviceof the packet.
 7. The method of claim 6, wherein the source device is asource base station or a source UE.
 8. A method comprising:transmitting, by a source device to a user equipment (UE), a packetcomprising a packet destination identifier (ID) that identifies adestination of the packet, wherein the packet destination identifier isa higher layer ID that is configurable, and wherein the packet isforwarded to a target device by the UE based on the packet destinationidentifier.
 9. The method of claim 8, wherein the packet destinationidentifier is different from a radio network temporary identifier (RNTI)of the target device.
 10. The method of claim 8, wherein the packetdestination identifier uniquely identifies the target device as a finaldestination of the packet.
 11. The method of claim 8, wherein the packetdestination identifier is the higher layer ID multiplexed into a dataportion of the packet.
 12. The method of claim 8, wherein the sourcedevice is a source base station or a source UE.
 13. The method of claim8, wherein the target device is a target base station or a target UE.14. A first user equipment (UE) comprising: at least one processor; anda non-transitory computer readable storage medium storing programming,the programming including instructions that, when executed by the atleast one processor, cause the first UE to: receive a packet comprisinga packet destination identifier (ID) that identifies a destination ofthe packet, wherein the packet destination identifier is a higher layerID that is configurable; and forward the packet to a second UE or a basestation based on the packet destination identifier.
 15. The first UE ofclaim 14, wherein the packet destination identifier is different from aradio network temporary identifier (RNTI).
 16. The first UE of claim 14,wherein the packet destination identifier uniquely identifies the secondUE as a final destination of the packet or uniquely identifies the basestation as the destination of the packet.
 17. The first UE of claim 14,wherein the packet destination identifier is the higher layer IDincluded in a self-contained bit field.
 18. The first UE of claim 14,wherein the packet destination identifier is the higher layer IDmultiplexed into a data portion of the packet.
 19. The first UE of claim14, the instructions to cause the first UE to receive the packetincluding instructions to cause the first UE to: receive the packet froma source device of the packet.
 20. The first UE of claim 19, wherein thesource device is a source base station or a source UE.
 21. A sourcedevice comprising: at least one processor; and a non-transitory computerreadable storage medium storing programming, the programming includinginstructions that, when executed by the at least one processor, causethe source device to: transmit, to a user equipment (UE), a packetcomprising a packet destination identifier (ID) that identifies adestination of the packet, wherein the packet destination identifier isa higher layer ID that is configurable, and wherein the packet isforwarded to a target device by the UE based on the packet destinationidentifier.
 22. The source device of claim 21, wherein the packetdestination identifier is different from a radio network temporaryidentifier (RNTI) of the target device.
 23. The source device of claim21, wherein the packet destination identifier uniquely identifies thetarget device as a final destination of the packet.
 24. The sourcedevice of claim 21, wherein the packet destination identifier is thehigher layer ID multiplexed into a data portion of the packet.
 25. Thesource device of claim 21, wherein the source device is a source basestation or a source UE.
 26. The source device of claim 21, wherein thetarget device is a target base station or a target UE.